Visio Homepages

Overview

A process library homepage is usually formed from HTML5, or perhaps Flash, if an older design. Even older homepages may be Visio files exported to HTML. Whatever the type of homepage, some features of its implementation should be consistent so that URLs that are used commonly to target the homepage work correctly.

IMPORTANT: A Visio homepage shouldn't be used if a theme is set for a site. Themes are the current, standard way of implementing a custom homepage and formatting styles for a site. The redirection behaviour when a theme is set for a site targets a homepage defined by the theme, and not the files exported by Visio.

Implementing a Visio Homepage

Visio File

The homepage Visio file should be in the map store, typically:

Triaster\TriasterServer2011\

MapStore\

Library\

Menu Pages\

Prelive + Live\

Homepage.vsdm

Sandpit\

Homepage.vsdm

Note:

The file's extension has been depicted as '.vsdm', but could be '.vdx' or '.vsdx', depending on the version of Visio and whether the file contains VBA.
A 'Prelive + Live' folder is depicted, but there may be separate 'Prelive' and 'Live' folders.

These Visio files are exported to HTML in a site publication.

Triaster\TriasterServer2011\

ProcessLibraries\

Library\

Site\

html\

homepage.map page-1_files\

homepage.map page-1.html

Retaining the Homepage HTML

Menu page Visio files (including homepages) are published separately from process map Visio files, and aren't included in the published Catalogue. A publication feature, Delete Obsolete HTML, uses the Catalogue as a reference for current HTML. Any HTML without a corresponding record in the Catalogue will be identified as obsolete, and will be deleted. To prevent the deletion of menu page HTML, exclusions need to be specified in this file:

Triaster\TriasterServer2011\

ProcessLibraries\

Library\

Site\

Tools\

listofhtml.xml

Exclusions will be of this form:

</triaster>

<user>

<htmlurl>/html/homepage*.html</htmlurl>

</user>

</htmlfilestoretain>

If there are other Visio-based menu pages, then there would need to be exclusions for them too, e.g.

</triaster>

<user>

<htmlurl>/html/homepage*.html</htmlurl>

<htmlurl>/html/hrmessage*.html</htmlurl>

<htmlurl>/html/knowledge*.html</htmlurl>

<htmlurl>/html/libraryadministration*.html</htmlurl>

<htmlurl>/html/librarysearch+reports*.html</htmlurl>

<htmlurl>/html/processmapskey*.html</htmlurl>

<htmlurl>/html/usermessage*.html</htmlurl>

</user>

</htmlfilestoretain>

As there are no references to specific sites in these exclusions, a copy of the 'listofhtml.xml' file can be used in each library site's 'Tools' folder.

Targeting the Homepage

There are numerous ways in which a Homepage may be targeted, and different forms of URLs that may be used. The important thing is that, ultimately, there is a common target.

These are files that are pertinent in determining linking to a homepage.

Triaster\TriasterServer2011\

Menupage Templates\

toolbar_1.txt

ProcessLibraries\

Library\

Site\

html\

homepage.map page-1_files\

main_2.html

homepage.map page-1.html

static html\

home.html

homepageinner.html

index.htm

toolbar_1.txt

This file is a template from which the toolbar - HOME SEARCH REPORTS etc - is constructed. Links are defined within it.

<liPLACE_HOLDER_SELECTED_HOME><a href="frames.aspx?tool=home&library=PLACEHOLDER_LIBRARY&site=PLACEHOLDER_SITE" target="_parent"PLACE_HOLDER_TOOLBARS_HOME>Home</a></li>

The HOME URL could be changed here.

By default, there is a single file that all sites are configured to use. Custom copies could be made and associated with sites. However, this isn't recommended if alternative methods of achieving the same end are available. Indeed, in the implementation described here, this file remains unchanged.

main_2.html

This is a file created by the Visio export. This defines the main content of the Visio homepage.

homepageinner.html

When not using a theme, this will define the homepage main content, whether directly or through forwarding behaviour. This is regarded as the common landing page, however the homepage is targeted.

When implementing a Visio homepage, it forwards to 'main_2.html', which is created when the Visio homepage file is exported. The HTML content becomes:

<html>

<head>

</head>

</body>

</html>

index.htm

This file forwards to 'home.html', which is assumed to be a frameset that incorporates 'homepageinner.html'. This is a standard file, and remains as it is.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>

<head>

</head>

</body>

</html>

Remove theme setting

If a theme is set for the site, remove that setting in Edit Configuration by configuring the theme as 'Default'.

Disable HTML5 Homepage

Usually, an HTML5 homepage is configured, using either a 'click' or a 'hover' design. This needs to be disabled.

Triaster\TriasterServer2011\Settings\

Settings.xml

...

...

...

Publish the site

The site needs to be published to produce the homepahe HTML.

Summary

Implementing a Visio-based homepage can be summarised as:

Create the homepage in Visio, and save it to the appropriate menu pages location.
Configure the homepage file in the 'listofhtml.xml' files of the library so that the HTML isn't deleted when maps are published.
Recreate 'homepageinner.html' with the HTML code described.
Ensure a theme isn't set for the site.
Ensure an HTML5 homepage type isn't set for the site.
Publish the site.